Optimized flow control for water infrastructure

ABSTRACT

Apparatuses, systems, and methods for optimizing and adjusting water usage are described. An example method may include receiving water usage data and determining a peaking factor for water usage. The peaking factor may be associated with water usage at a flow controller. A flow controller can control various types of water outlets, such as a water sprinkler for a residential home. The flow controller may be positioned along a main water supply to a property or home. The method may also include determining that the peaking factor passes a threshold water usage for the flow controller and adjusting a watering schedule of the flow controller based partly on the determination that the peaking factor passed the threshold water usage.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C.§119 to U.S. ProvisionalApplication No. 62/373,686 entitled “Optimized Flow Control for WaterInfrastructure,” filed Aug. 11, 2016, which is incorporated herein byreference, in its entirety, for any purpose.

FIELD

The present disclosure relates generally to controlling and improvingflow control and fluid usage for fluid systems.

BACKGROUND

Water infrastructure, such as water reservoirs, piping systems, andtreatment plants are designed around a particular population, density,or water usage estimate. However, often, population growth or waterdemand vastly increases over the original design constraints of thewater infrastructure. This can lead to various issues, includingsignificant drops in water pressure at any particular water outlet(e.g., hose or shower in a house), damage to delivery pipes and otherinfrastructure, as well as overextension of certain water sources, suchas reservoirs or other water stores. Currently, utility companies arelimited in their ability to manage the water system and infrastructureand rebuilding or renovating such infrastructure is not only timeintensive, but also expensive, and typically exceeds the budgets for anygoverning body.

Further, changes in landscape, climate, as well as water availability,water cost, and the like, may affect the watering demands or a desiredwatering schedule for a particular property. However, often times thesevariations are not readily available or apparent to a property owner andthus the property owners do not adjust watering schedules accordingly.

SUMMARY

In one embodiment, a method for optimizing water usage in a waterinfrastructure is described. The method includes receiving by one ormore flow controllers usage data corresponding to demand on the waterinfrastructure, adjusting by a processor in a server or in the one ormore flow controllers a water usage schedule for one or more propertiesbased on the usage data, and activating by the one or more flowcontrollers one or more water outlets for the one or more propertiesbased on the adjusted water usage schedule.

In another embodiment, a method for adjusting water usage in a waterinfrastructure is described. The method includes receiving water usagedata and determining a peaking factor for water usage, where the peakingfactor is associated with water usage at one or more flow controllers.The method may also include determining that the peaking factor passes athreshold water usage for the one or more flow controllers and adjustinga plurality of watering schedules based partly on the determination thatthe peaking factor passed the threshold water usage, where each wateringschedule is associated with a corresponding flow controller of the oneor more flow controllers.

In yet another embodiment, a system is described that includes a servercoupled to infrastructure databases and a plurality of flow controllers,where each flow controller of the plurality of flow controllersconnected to at least one water outlet of a plurality of water outlets.The server also includes a non-transitory computer readable media andconfigured to execute instructions stored on the non-transitory computerreadable media. The instructions include determining a peaking factorfor water usage based partly on water usage data received from at leastone flow controller of the plurality of flow controllers, where thepeaking factor is associated with water usage at the plurality of flowcontrollers. The instructions also include adjusting a plurality ofwatering schedules based partly on the peaking factor, where eachwatering schedule is associated with a corresponding flow controller ofplurality of flow controllers.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system for optimizing and varying flowcontrol for a fluid delivery infrastructure.

FIG. 2 is a simplified flow diagram illustrating a utility that may beoptimized with the system of FIG. 1.

FIG. 3 is a flow chart illustrating a method of the system of FIG. 1 tomodify water usage for various properties based on capacity and demand.

FIG. 4 is a flow chart illustrating a method for adjusting flowcontroller settings and characteristics.

FIG. 5 illustrates an example of a chart comparing outdoor water usageand indoor usage over time.

FIG. 6 is a flow chart illustrating a method for generating updateduniversal settings for multiple flow controllers.

FIG. 7 is a flow chart illustrating a method for modifying local flowcontroller settings using a universal template change.

FIG. 8 is a flow chart illustrating a method for adjusting wateringschedules.

FIG. 9 is a flow chart illustrating a method for compensating a peakingfactor.

FIG. 10 is a simplified block diagram of a computing device that can beused by one or more components of the system of FIG. 1.

SPECIFICATION

In some embodiments herein, an optimization flow control system forfluid infrastructure systems is disclosed. The optimization systemincludes multiple flow controllers that control flow to one or more flowdevices or outlets in a property, external infrastructure and waterdata, as well as dynamic real-time monitoring of flow usage to enhancethe flow patterns for a plurality of devices. In one embodiment, thesystem is employed to adjust the watering schedules based on time and/orday for a select number of properties. The properties may includeresidential areas (e.g., houses, surrounding lands, pools, yards, etc.),as well as commercial areas, common areas (e.g. grounds controlled by ahome owner's association, complexes, or the like), as well as city orgovernment properties (e.g., parks, medians, governmental buildings, orthe like). In some instances, the properties may be grouped together bylocation, such as zip code, geography, or the like, and often may belinked based on a common water source or water delivery infrastructure(e.g. those properties that share a main fluid line).

The system stagers watering usage times, such as sprinkler valveoperation or irrigation system operation, based on water data includingpeak water time for a particular infrastructure. For example, the systemmay stagger the outdoor watering schedules for five properties to ensurethat all five properties do not water simultaneously and reduce largedemands on the water infrastructure. By staggering the water demand, thesystem can alleviate issues and reduce the effect of limitations of anoutdated or outgrown water infrastructure. In particular, while a mainwater line to a residential neighborhood may be designed to handle adensity of 200 homes and currently there are 400 homes receiving wateraccess from the main water line, by staggering the demand of the 400homes, the water infrastructure can continue to serve each home with adesired or intended water flow pressure and water flow volume withoutdamage to the water infrastructure.

In some embodiments, the optimization system may take into account notonly water infrastructure limitations, but also usage patterns, densitychanges, and other variations over time. In this manner, theoptimization system can satisfy the competing issues of on-demandwatering, homeowner expectations, and limited resources andinfrastructure capabilities.

In addition to the optimization system, the current disclosure alsoincludes a method of adjusting local settings of groups of flowcontrollers using a global process. In particular, based on changes inwater availability, climate, weather, new water infrastructure, orvegetation, the method may generate new templates or universal settingsthat can be used by individual flow controllers to adjust individualizedwater schedules accordingly. For example, a user can generate an updateto a current model or a new model that can then be pushed down tomultiple devices simultaneously. The updated model then can be used byeach device individually to make specific changes to a wateringschedule. As a specific example, an evapotranspiration (ETo) value ormodifier can be adjusted based on changes to one or more propertycharacteristics and this value is then transmitted to all of theaffected flow controllers, which then use the updated value to adjustwatering schedules accordingly. As another example, a precipitationtolerance value can be transmitted to the flow controllers that then useit to update the watering schedules accordingly. By transmitting thechanges or new values to multiple controllers as a universal setting ortemplate, the system does not have to individually adjust the multiplewatering schedules to adjust for the changes. This saves significantresource time as often watering schedules are individualized based on auser's preferences, specific characteristics of the vegetation andproperty watered by the flow controller, and the like, and adjustingeach schedule individually would require significant resources and betime intensive.

Turning now to the figures, the system of the present disclosure will bediscussed in more detail. FIG. 1 is a block diagram illustrating anexample of a flow optimization system 100. The system 100 includesmultiple flow controllers 102 a, 102 n that are connected to and controla plurality of water outlets, such as a sprinkler valves, 104 a, 104 b,104 c. The system 100 also includes one or more servers 106, userdevices 108 a, 108 n and one or more infrastructure databases 112. Eachof the various components may be in communication directly or indirectlywith one another, such as through a network 110. In this manner, each ofthe components can transmit and receive data from other components inthe system. In many instances, the server 106 may act as a go betweenfor some of the components in the system 100.

The network 110 may be substantially any type or combination of typescommunication system for transmitting data either through wired orwireless mechanism (e.g., WiFi, Ethernet, Bluetooth, cellular data, orthe like). In some embodiments, certain components in the system 100 maycommunicate via a first mode (e.g., Bluetooth) and others maycommunicate via a second mode (e.g., WiFi). Additionally, certaincomponents may have multiple transmission mechanisms and be configuredto communicate data in two or more manners. The configuration of thenetwork 110 and communication mechanisms for each of the components maybe varied as desired and based on the needs of a particularconfiguration or property.

The flow controllers 102 a, 102 n are substantially any type of devicethat controls or regulates flow to one or more flow devices or outlets104 a, 104 b. In one embodiment, the flow controllers 102 a, 102 n aresmart sprinkler controllers that control the operation of a plurality ofsprinkler valves in one or more watering zones for a particular propertyor area (e.g., residential property). An example of a sprinklercontroller that may be used with the system 100 can be found in U.S.Publication No. 2015/0319941 filed on May 6, 2014 and entitled“Sprinkler and Method for an Improved Sprinkler Control System,” whichis incorporated by reference herein in its entirety. The sprinklervalves may be electronically operated, such as one or more solenoidvalves, that open and close a flow path to a sprinkler head.

In other embodiments, the flow controllers 102 a, 102 n control varioustypes of water outlets, and may be positioned along a main water supplyto a property or home. For example, the flow controllers 102 a, 102 nmay be configured to turn on or turn off flow for a particular propertysuch as a valve controller connected to a main water supply line. Inthese embodiments, the outlets 104 a, 104 b, 104 c may be different fromone another, e.g., sprinkler valve, showerhead, toilet, washing machine,dishwasher, or the like. In this manner, it should be understood thatthe discussion of any particular flow outlet or flow controller is meantas illustrative only.

The server 106 is a computing device that processes and executesinformation. The server 106 may include its own processing elements,memory components, and the like, and/or may be in communication with oneor more external components (e.g., separate memory storage) (an exampleof computing elements that may be included in the server 106 isdisclosed below with respect to FIG. 8). The server 106 may also includeone or more server computers that are interconnected together via thenetwork 110 or separate communication protocol. The server 106 may hostand execute a number of the processes exceed by the system 100 and/orthe flow controllers 102 a, 102 n. In some embodiments, each of flowcontrollers 102 a, 102 may communicate with specialized servers 106 thatcommunicate with a specialized system server 106 or each may communicatewith the same server 106 or groups of servers.

The user devices 108 a, 108 n are various types of computing devices,e.g., smart phones, tablet computers, desktop computers, laptopcomputers, set top boxes, gaming devices, wearable devices, or the like.The user devices 108 a, 108 n provide output to and receive input from auser. For example, the server 106 may transmit one or more alerts to theuser devices 108 a, 108 n to indicate information regarding the flowcontroller 102 a, 102 n, the water outlets 104 a, 104 b, 104 c, and/orthe property being watered. The type and number of user devices 108 a,108 n may vary as desired and may include tiered or otherwise segmentedtypes of devices (e.g., primary user device, secondary user device,guest device, or the like).

The infrastructure databases 112 store or include access to data and/orsensors from various devices or information hubs. The infrastructuredatabases 112 may include computing devices, such as servers, userdevices, or the like, that include data on environmental factors (e.g.,weather tracking), utility information (e.g., average water usage for aneighborhood or house, average water pricing rates, wateringrestrictions, etc.), water reservoir or water source information, smarthome devices (e.g., smart thermostat, alarm system), sensor data, or thelike. The infrastructure databases 112 may be substantially any deviceor group of devices that provide environmental or external data that isrelevant or correlates to the system 100. In some embodiments, theinfrastructure databases 112 include data corresponding to a waterutility information, such as reservoir level or percentage, deliverycapacity (e.g., pipe diameter), historical use, predicted use, andfuture developments or construction.

FIG. 2 is a simplified flow diagram illustrating an infrastructure thatmay be optimized with the system 100. With reference to FIG. 2, theutility includes one or more water sources 120 that supply water via amain supply 122 to multiple properties 130 a, 130 b, 130 c, 130 d, 130e, 130 f directly or through one or more branches 124, 126, 128. Thewater source 120 may be a reservoir, water tank, lake, pond, river,stream, etc. that is used (solely or in part) to deliver water to theproperties 130 a-130 f. The infrastructure database 112 may include datacorresponding to the level of the water source 102, such as the fillheight, used percentage, or the like, that is used to correlate waterusage as compared to water replenishment.

The water source 120 is fluidly connected to a main water supply 122.The main supply is defined as being the main source for a particulargrouping of properties and may not be the “main” supply directly fromthe water source, but rather a branch from a city or larger area widewater system. The main water supply 122 is typically a pipe or otherflow pathway that transports fluid from the water source 120 (or frommultiple water sources) to individual water outlets at the one or moreproperties 130 a-130 f. The main supply 122 is typically difficult toaccess and may be buried other otherwise concealed by roadways,structures, or the like.

Often, the main supply 122 is configured to supply a particular numberof properties or people, e.g., 100 homes or 600 people. Because the mainsupply 122 is typically fixed in size and selected based on a predictednumber of people, the amount of water that it can deliver to downstreamproperties may be predetermined and may be outdated based on the growthor eventual use of the properties. The main supply 122 includes one ormore fluid branches 124, 126, 128 that fluidly connect to the variousproperties 130 a-130 f. Each of the properties 130 a-130 f may beconnected via one or more branches, for example, each property may befluidly connected through a branch off of the main supply 122, as wellas a property specific branch that connects directly to the property.However, in other examples, other delivery pathways may be used.

The water source 120 is a reservoir or other type of storage componentthat stores or provides water for use with a particular area of set ofproperties. In some instances, the water source 120 may be configured toserve multiple properties through many different branches (e.g., acity's reservoir), but in other instances, the water source 120 may bemore localized to a smaller set of properties, such as an irrigationpond in a housing development. Other water sources 120 include naturalor man-made water supplies, such as underground reservoirs, rivers,desalination plants, or the like. In many instances, the water source120 may have a predicted or known water capacity that can be used todetermine an allotted water amount for any particular property 130 a-130f receiving water from the water source 120. The water capacity may beincreased or decreased based on the precipitation levels for aparticular year or variations in the demand.

With reference to FIGS. 1 and 2, each of the properties 130 a-130 f, orselect groups of the properties 130 a-130 f (e.g., two or moreproperties), include a flow controller 102 a. The flow controller 102 adetects water flow usage by the one or more properties 130 a-130 ffluidly connected to the controller 102 a as discussed above. In someembodiments, each of the properties 130 a-130 f (or a large number ofthe properties) includes a controller 102 a such that the water usage ofthe main supply 122 can be detected and tracked.

In some embodiments, the system 100 may be used to control and track thewater usage of multiple properties, e.g., a plurality of residentialhomes, an apartment or condominium complex, commercial complex (e.g.,business park), or the like. In these embodiments, the system maycommunicate with multiple flow controllers 102 a-102 f for each of thevarious properties. Each of the properties 130 a-130 f include indoorflow sources and outdoor flow sources 104 a-104 c. These flow sourcesmay be connected to one or more flow controllers 102 a-102 n In someembodiments, the flow controllers 102 a-102 n may be configured todistinguish indoor water usage from outdoor water usage for eachproperty 130 a-130 f, but in other examples, the flow controllers 102a-102 n may be configured to detect overall usage for the property 130a-130 f (regardless of the type) or may be configured to detect eitherindoor/outdoor or a specific type of use (e.g., sprinkler/irrigationuse). The type of water usage detected may be by the controllers 102a-102 n directly or indirectly.

FIG. 3 is a flow chart illustrating a method of the system 100 to modifywater usage for various properties 130 a-130 f based on capacity anddemand. With reference to FIG. 3, the method 200 may begin withoperation 202 and the server 106 receives property usage data from theone or more controllers 102 a-102 n. The property usage data iscollected and stored by each controller 102 a-102 n at one or more ofthe properties 130 a-130 f and is detected through monitoring the waterusage of each property (or group of properties). For example, each ofthe controllers 102 a-102 n may detect the time, amount, and dates ofoutdoor irrigation for a select property 130 a-130 f. Additionally oralternatively, each of the controllers 102 a-102 n may detect indoorwater usage times, amounts and dates (e.g., water usage corresponding toshowers, baths, dishwashers, washing machines, or the like). This waterusage data for each property 130 a-130 f is transmitted by therespective controller 102 a-102 n to the server 106 through the network110.

After operation 202, the method 200 may proceed to operation 204. Inthis operation 204, the server 106 receives the water and location datafrom the one or more infrastructure databases 112. The water andlocation data corresponds to information corresponding to the watersource 120, main supply 122, and optionally location data correspondingto the properties 130 a-130 f. For example, the water source 120 dataincludes information regarding the fill level (e.g., 100%, 80%, or thelike), the main supply 122 data may include information corresponding tothe diameter of flow pipes and/or branches 124, 126, 128, as well as thenumber of properties fed from the main supply 122. Other infrastructuredata that is transmitted to the server may include census or populationdata corresponding to the number of people in the location served by thewater source 120 or main supply 122, the number of properties within theservice area, the predicated usage for a select time frame, as well ashistorical usage, weather patterns, other available water sources, suchas water rights information (e.g., water legal entitlements) that couldinclude information regarding other water sources that may be purchased(outside of water source 120) and/or data from other water districtsthat may be purchased or swapped, as well as information on thebeginning of the water source (e.g., lower or upper basin). The types ofinfrastructure data from the infrastructure databases 112 may be variedbased on the type of tracking and control desired.

Additionally, it should be noted that the examples may be inputs storedwithin the server 106, rather than pulled dynamically from the databases112. For example, when the system 100 is initially activated, a user mayinput certain infrastructure data, such as data that may not change yearto year (e.g., infrastructure capacity, pipe diameters, etc.), that theserver 106 can reference. Other data, such as property numbers,population, usage, etc. may be input dynamically or at select timeperiods (e.g., a few times a year, once a month, or the like).

With continued reference to FIG. 3, after operation 204, the method 200may proceed to operation 206 and the server 106 analyzes the currentdemand. In particular, the server 106 compares the property usage datafrom operation 202 to the infrastructure data from operation 204 todetermine the current demands and usage of the water system. Byanalyzing the demand, the server 106 may determine peak usage times forwater, typical amounts of water, stresses exhibited on the main supply122, branches 124, 126, 128, and/or water source 120, as well as othertrends and data corresponding to the After operation 206, the method 200may proceed to operation 208 and the server 106 determines whether thereis a predicated increase in the demand on the water infrastructure. Forexample, the server 106 may determine that a new development ofresidential properties is being added to a particular location that willneed to access a select water source 120 or main supply 122. As anotherexample, the server 106 may assess the current water usage for each ofthe properties 130 a-130 f and determine that the water usage has beenincreasing over the original demand or predicted usage, such as due to adrought and need for more irrigation for vegetation. Other examplesinclude analyzing economic data regarding the geographic location,climate change data (e.g., temperature, vegetation, insect infestation,changes in snowpack, forest fires, and thinning of forest information)as well as other types of growth information to assess whether thelocation may experience a growth in population and/or properties in thefuture.

If an increase in water demand is expected, the method 200 may proceedto operation 210 and the server 106 may adjust one or more settings foreach of the flow controllers 102 a-102 n in the select area. Thesettings may include watering amounts, watering schedules, notificationtypes or frequency, providing usage information to property owners, orthe like. The types of settings that may be adjusted may be varied basedon the type of increase predicted, as well as the type of water sourcescontrolled or monitored by the flow controllers 102 a-102 n. The sever106 may push the settings changes to multiple controllers 102 a-102 nsimultaneously, individually, or in select groupings (see FIGS. 4, 6,and 7).

If no increase is predicted in operation 209 or after the settings havebeen adjusted in operation 210, the method 200 may proceed to operation212. In operation 212, the server 106 may determine whether the currentwater levels in the water source 120 are sufficient for the current orpredicted usage. For example, the server 106 may analyze the usage data,along with infrastructure data from the infrastructure databases 112 todetermine whether the current or expected water levels in the watersource 120 can handle the current and expected demand. The analysis mayinclude current demand, predicted demand, as well as current waterlevels. If the water source 120 is above capacity (e.g., 130%), thenalthough an increase in demand may be expected, the server 106 maydetermine that the water levels of the water source 120 are sufficient.As another example, if the water source 120 is below capacity and anincrease in demand is expected, then the water levels may be determinedto be insufficient. The analysis may vary based on the water source 120,the location area, as well as other factors including weather patterns,growth, or the like. In some embodiments, operations 208 and 212 may becombined together in a single analysis performed by the server 106 todetermine whether anything should be adjusted in light of predictedusage and water levels.

If in operation 212 the server 106 determines that the water levels areinsufficient, the method 200 may proceed to operation 214. Operation 214may be similar to operation 210 and the server 106 may adjust one ormore settings or characteristics of the flow controllers 102 a-102 n toaccount for the expected water levels. For example, if the water source120 is low, the server 106 may instruct each of the flow controllers 102a-102 n to reduce outdoor watering times or other usage by a particularpercentage in order to save water. As another example, if the watersource 120 is high, the server 106 may allow increases in watering timesor schedules. Additionally, other settings that can be modified includeuser notification types and frequency, water restriction times, waterpricing (e.g., dynamic pricing may be used during peak demands), zonemodifications (e.g., platform can offer rebate dollars to switch out aportion of the grass zones to a less water-intensive type ofvegetation), or options to switch out certain water fixtures such asmore water efficient sinks, toilets, and the like.

In both operations 208 and 212, the sever 106 may make dynamicadjustments based on the predicted usage and water levels and/or mayinclude input from utility or government entities. For example, theserver 106 may provide or receive usage and water level data from one ormore outside entities, that may also provide guidance to adjust settingsfor the flow controllers. In other examples, the server 106 may adjustthe flow controllers 102 a-102 n using the infrastructure and usage datawithout input from external entities. The level of input and control ofutilities or government entities may vary based on the location and thenumber of controllers, as well as the structure of the system 100.

After operation 212, the method 200 may proceed to operation 216 and theserver 106 may transmit the various property and location data updatesto the flow controllers 102 a-102 n and/or user devices 108 a-108 n. Asnoted above, in some embodiments, the server 106 may transmit changes tothe flow controllers 102 a-102 n in groups simultaneously, individually,or in select groups. Additionally, in some embodiments, the server 106may transmit setting adjustments and/or usage and water data. That is,in some instances, the server 106 may adjust various settings of theflow controllers themselves, but in other embodiments, the server 106may provide updated data to the flow controllers 102 a-102 n which maythen make any changes locally. In some instances, the server 106 mayadjust select settings globally for a set of flow controllers and othersettings may be adjusted locally by the flow controllers 102 a-102 n bythemselves.

A method for adjusting the flow controllers 102 a-102 n based on waterusage data, water source 120 data, and infrastructure data will now bediscussed. FIG. 4 is a flow chart illustrating a method for adjustingflow controller settings and characteristics. With reference to FIG. 4,the method 250 may begin with operation 252 and the flow controller 102a-102 n receives property and user input data. The property and userinput data may include data corresponding to the property 130 a-130 fthat the flow controller 102 a-102 n is connected to, e.g., vegetationtype, soil characteristics, weather patterns, number of sprinklervalves, number of zones, property area, water source outlet information(e.g., types of houses, sprinkler valves, showerheads, toilets, etc.),as well as the number of controllers 102 a-102 n (e.g., some propertiesmay have more than one controller). The property and user input data maybe input directly into the controller 102 a-102 n by the user, such asthrough an input/output interface, or may be received from thecontroller 102 a-102 n via the server 106 or other computing device. Insome embodiments, the controller 102 a-102 n may also detect propertyinformation such as through one or more flow sensors, calibrationpatterns, or the like.

After operation 252, the method 250 may proceed to operation 254. Inoperation 254, the flow controller 102 a-102 f receives location usagedata from the server 106. This data includes the water usage information(e.g., historical and predicted use), water levels, and otherinfrastructure data from the infrastructure databases 112. The locationusage data may be transmitted to the flow controllers 102 a-102 n aspart of operation 216 in method 200 (e.g., as raw data or adjustedsettings for the flow controllers), or may be transmitted separatelyfrom the server 106 as raw data or directly from the infrastructuredatabases 112.

After operation 254, the flow controller 102 a-102 n selects scheduleand system settings. The schedule may include a watering schedule, suchas for irrigation and other outdoor usage, as well optionally indoorwater use schedules, such as run times for washing machines,dishwashers, and other elements. In embodiments where the wateringschedule corresponds to an irrigation schedule, the schedule includestimes, dates, and run-times for various sprinkler valves, which may bedetermined by sprinkler zones having multiple valves, or on avalve-by-valve basis. The schedule will determine the operation ofmultiple water outlets for the property 130 a-130 f.

In a specific example, the flow controller 102 a-102 n adjusts thewatering schedule for one or more properties 130 a-130 n to adjust forpeak demand on the main supply 122. For example, most properties 130a-130 n fluidly connected to the main supply 122 may require water usageduring the weekday morning hours of 6 am to 9 am while people aregetting ready for work, as well as watering outdoor vegetation. Usingthe usage data, the flow controller 102 a-102 n may select an outdoorwatering schedule that is outside of the peak usage times, e.g., eitherbefore or after the 6-9 am hours in order to reduce the overall demandon the main supply 122 during this time. As the peak demand informationmay be transmitted to multiple flow controllers 102 a-102 n within aparticular geographical location, the demand on the main supply 122 maybe reduced and even though the main supply 122 may serve a largepopulation or property number than its original design was intended todo, by spacing out the demand over a period of time, the main supply 122and other infrastructure (e.g., water supply 120 and branches 124, 126,128) can accommodate the growing demand and usage.

Other types of adjustments may be determined dividing properties 130a-130 n into select groups, either based on geographic location, addresstype, typical watering demands, or the like, and the flow controllers102 a-102 n can select schedules for each of these properties ensuringthat certain properties activate their outdoor usage together. Forexample, if a first property 130 a has a large outdoor watering demandand a second property 130 b has a low outdoor watering demand, the flowcontrollers 102 a-102 n for each of these two properties may coordinate(via the server 106) such that the two properties can operate together.On the contrary, a third property 130 c may have a large outdoor demandas well and the system 100 may help to ensure that the first property130 a and the third property 130 c do not activate their outdoorirrigation systems at the same time or day, reducing the overall loadfor the infrastructure.

As another example, the flow controllers 102 a-102 n for certainproperties 130 a-130 n may be set to activate on certain days of theweek, and other flow controllers for other properties may be set toactivate on the other days of the week. In this manner, each of theproperties 130 a-130 n served by the main supply 122 may bealternatingly activated, such that all of the properties are notactivated together. This spaces out the demand on the system, allowingfor the system to more easily accommodate growing demand, as well asunexpected changes to the water resource levels.

After operation 256, the method 250 may proceed to operation 258. Inoperation 258, the flow controller 102 a-102 n may transmit the scheduleor settings to the user devices 108 a-108 n. The flow controller 102a-102 n may transmit the schedule or settings either directly orindirectly to the user devices 108 a-108 n (e.g., through the server106) or directly via the network 110. The transmission to the userdevice 108 a-108 n may include data corresponding to the selectedschedule (e.g., watering times for a particular sprinkler zone), as wellas other data, e.g., usage data compared to surrounding properties,infrastructure data, or the like. The type of data transmitted to theuser device 108 a-108 n may be varied as desired.

After operation 258, the method 250 may proceed to operation 260 and theflow controller 102 a-102 n may operate. In this manner, the flowcontroller 102 a-102 n may control the various flow outlets for theproperties 130 a-130 n based on the schedule, e.g., activate sprinklervalves on a predetermined schedule, provide user notifications, andactivate other elements. The operation of the controller 102 a-102 n mayinclude dynamic variations based on changes to weather, vegetation, userdemands, or the like.

With continued reference to FIG. 4, after operation 260, the method 250may proceed to operation 262. In operation 262, the flow controller 102a-102 n determines whether an update to the settings and schedule may bedesired. For example, the flow controllers 102 a-102 n may check everyfew months (e.g., on a quarterly basis) or other select time period forupdated data that could vary the settings for the devices. Alternativelyor additionally, the flow controllers 102 a-102 n may be selected tocheck for updates based on communications from the server 106, userinput, randomly, or based on other changes to the property (e.g.,changes in vegetation, weather, or soil). If the flow controllers 102a-102 n are to be updated, the method 250 returns to operation 254.However, if the flow controllers 102 a-102 n do not need to be updated,the method 250 may return to operation 260 and continue to operate theflow controllers 102 a-102 n.

Using the methods 200, 250 of FIGS. 3 and 4, the system 100 can optimizewatering for various properties 130 a-130 n that can allow overtaxedinfrastructure to be able to accommodate current demand, as well asexpanding demands. FIG. 5 illustrates an example of a chart comparingoutdoor water usage 270 and indoor water usage 272. As shown in FIG. 5,outdoor water usage, such as a due to irrigation, peak demand can be 2.5to 3 times that of the baseline usage (e.g., typical indoor usage 272).As shown in FIG. 5, outdoor watering can generate a large demand on theinfrastructure and main supply 122 for small periods of time. By usingthe methods 200, 250 the outdoor demand can be more evenly spaced acrosstime to reduce the demand peaks, reducing the peak load on the mainsupply 122 and other components of the water infrastructure. Becausewater infrastructure may be designed to accommodate peak demand, bysmoothing the peaks and evenly distributing the demands across multipletime periods, older infrastructures can be configured to handleincreases in demand, without structural changes to the system.

In some embodiments, the system 100 may provide updated settings togroups of controllers 102 a-102 n simultaneously. The settings can thenbe used to adjust the particular watering schedule of controllers thatmay be individually customized or selected based on user and propertycharacteristics and preferences. For example, in some instances, changesto water infrastructure or demand, weather patterns, vegetation, or thelike, may affect a large number of properties. Individually adjusting awatering schedule for each controller 102 a-102 n would be a time anduser intensive process and not possible for certain users (e.g.,landscapers or large property owners) that operate multiple controllers102 a-102 n.

FIG. 6 is a flow chart illustrating a method 300 for generating updateduniversal settings for multiple controllers. FIG. 7 is a flow chartillustrating a method 310 for modifying controller settings based on auniversal template change. With reference initially to FIG. 6, themethod 300 may begin with operation 302 and the server 106 may receiveupdated setting data. The updated setting data may include changes suchas ETo values or percentages, perception tolerance that affects theamount of precipitation required to adjust a watering schedule,filtering of types of vegetation that could grow in a region withcustomer root depths set by the municipality to ensure proper wateringfor that type of plane in a specific region, filtering of soil typesspecific to a region, available watering dates (e.g., property addressescould be assigned watering windows based on odd or even addresses andthe controller then would determine how to fit the schedule within theassigned watering window). The updated setting data may be dynamicallydetermined based on various inputs to the server 106, input by a systemmanager, or the like. During this operation, a user may utilize anapplication program interface (API) that sets a select routine,protocol, and tools for creating a template for the controllers to modelthe new settings.

After operation 302, the method 300 proceeds to operation 304 and theserver 106 determines the controllers 102 a-102 n to be modified. Forexample, the server 106 may determine a particular setting change for aselect geographic region and then search for controllers 102 a-102 nwithin that region to be changed. As another example, the server 106 maydetermine a setting change that will affect only properties over acertain area and determine controllers that fit within that areadescription. Other factors include number of zones or valves controlledby a particular controller, types of vegetation within a particularzone, weather zone, user watering preferences, user (e.g., owner of thecontrollers), or the like.

Once the updated setting data is selected and the template created, andthe controllers 102 a-102 n to be modified have been determined, themethod 300 may proceed to operation 306. In operation 306, the server106 transmits the template to the select controllers 102 a-102 n. Forexample, the server 106 transmits the data as a software update to thecontroller, changing schedules and possibility restrictions on themanual control of the controller, altering the firmware. In someembodiments, most of the processing can be done be the server 106, butmay affect functionality of the hardware of the controller 102 a-102 n.In short, the updated setting data allows a user to avoid having toindividually adjust individual controllers to execute changes acrossmultiple devices, as the template (which may be user defined orautomatically defined by the server) can be used to dynamically adjustthe individualized settings.

Once the template has been transmitted to the controllers 102 a-102 n,the controllers 102 a-102 n can then use the template to adjustlocalized and individual settings. With reference to FIG. 7, in oneembodiment, the method 310 for receiving the templates from thecontrollers 102 a-102 n begins with operation 312 and the controllers102 a-102 n receive the updated template from the server 106. As notedabove with respect to operation 306, in this example, the controllers102 a-102 n may receive the template either directly or indirectly fromthe server 106 via the network 110 or through a hardwired or othercommunication mechanism.

After the controllers 102 a-102 n receive the template, the controllers102 a-102 n analyze the current watering schedules and settings based onthe updated template. For example, the controllers 102 a-102 n mayreview the current watering schedules and settings to determine whetherthe settings should be adjusted based on the global changes to atemplate, e.g., whether the vegetation, soil, weather, or the like, maybe included in the watering changes. In some instances the template mayonly affect certain types of vegetation or soil and the controller 102a-102 n may not include the affected type.

After operation 314, the method 310 may proceed to operation 316 and thecontroller 102 a-102 n may update schedule or settings based on thetemplate. In instances where the controller may include a schedule orsettings that are unaffected by the template change, the controller 102a-102 n may omit this operation. However, in instances where thetemplate will change variations in the schedule the controller 102 a-102n will update all individual and local settings to account for theglobal change.

As a specific example, the template may include a variation in a % ETomodifier that impacts a watering scheduling by changing the evaporationestimate for vegetation and soil. In this example, a change may reduceor increase a desired watering time and thus change the on/off times forparticular zones. As another example, the template may include a changein a precipitation tolerance that may apply to modifications in a setschedule, e.g., postpone or cancelation of a preset water schedule basedon a predetermined amount of precipitation. In this example, thecontroller 102 a-102 n may adjust or replace a software algorithm usedto determine whether a watering should be skipped or postponed.

After the flow controllers 102 a-102 n adjust the localized settings,the method 310 may proceed to operation 318 and the controllers 102a-102 n operate the system. The operation includes the select activationand/or monitoring of various water outlets.

Using the method 300, 310 of FIGS. 6 and 7, the system 100 can easilyadjust local settings for a large selection of controllers 102 a-102 nwithout requiring the server 106 to push through individual settings foreach of the controllers 102 a-102 n. This greatly enhances the speed andefficiency at which new settings can be implemented at a local level forspecific properties and controllers 102 a-102 n.

In particular, the template allows for a subscribe type of architectureas opposed to a publish architecture. With a publish type ofarchitecture, a water manager might receive a notification any time anew serialized controller is activated and then make updates to anynumber of settings individually for that controller. With the template,a subscribing architecture can be used where as soon as a new serializedcontroller is activated, the server 106 analyzes information about thatcontroller, say address, and then automatically assigns any number oftemplates to that controller based on its information, makingadjustments to the controller's settings without any interaction from awater manager. This helps to greatly increase the speed of the processfor registering a flow controller 102 a-102 n, especially in instanceswhere a manager or other user may have multiple flow controllers 102a-102 n across many properties that may have varying characteristics.

A method for adjusting the flow controllers 102 a-102 n based on waterusage data, water source 120 data, and infrastructure data will now bediscussed. FIG. 8 is a flow chart illustrating a method for adjustingflow controller schedules. With reference to FIG. 8, the method 400 maybegin with operation 404 and the server 106 receives water usage data,such as water trend data from a water utility, watering schedulesassociated with the flow controllers 102 a-102 n, or forecasted weatherdata. Some water usage data may be stored at a local database or memoryconnected to the server 106. In such a case, the server 106 may receiveusage data from the local database (e.g., infrastructure databases 112)or memory. For example, the server 106 may receive watering schedulesthat have been stored in local database based on a calculation orcomputation of the schedule according to the current watering schedulesand settings of the flow controllers 102 a-102 n.

Water usage data may also include property and user input data, such asdata corresponding to the property 130 a-130 f of the flow controller102 a-102 n (e.g., vegetation type, soil characteristics, weatherpatterns for the property, number of sprinkler valves, number of zones,property area), water source outlet information (e.g., types of houses,sprinkler valves, showerheads, toilets, etc.), as well as the number ofcontrollers 102 a-102 n. Water usage data may also include dataregarding changes, including but not limited to: ETo values orpercentages, perception tolerance that affects the amount ofprecipitation required to adjust a watering schedule, filtering of typesof vegetation that could grow in a region with customer root depths setby the municipality to ensure proper watering for that type of plane ina specific region, filtering of soil types specific to a region,available watering dates. Water usage data may also include dataregarding zones, including but not limited to: a number of zones orvalves controlled by a particular controller, types of vegetation withina particular zone, weather zone, user watering preferences, user (e.g.,owner of the controllers), or the like. Water usage data may alsoinclude location usage data, including but not limited to: water usageinformation (e.g., historical and predicted use), water levels, andother infrastructure data from the infrastructure databases 112.

After operation 404, the server 106 determines a peaking factor forwater usage at various associated (e.g., connected to server 106) flowcontrollers, such as flow controller 102 a-102 n, at operation 408. Asdescribed above with reference to FIG. 5, outdoor water usage 270 mayfluctuate with respect to indoor water usage 272, making peak demand upto 2.5 to 3 times that of the baseline usage (e.g., typical indoor usage272). The relative amount of fluctuation of the outdoor water usage 270with respect to the indoor usage 272 may be referred to as a peakingfactor. In some examples, a peaking factor may quantify the relativeamount of fluctuation with respect to outdoor water usage relative tobaseline overall water usage. For example, overall water usage may beboth outdoor and indoor water usage. A baseline water usage may refer toa water usage over a particular time-period. Accordingly, baselineoverall water usage may refer to outdoor and indoor water usage over amonth, day, hour, or the like.

A peaking factor may be quantified with respect to a time measure suchas an annual scale, a monthly scale (e.g., as shown in FIG. 5), a weeklyscale, a daily scale, an hourly scale, or the like. Overall water usagemay also fluctuate at certain hours in a day such that even during apeaking period (e.g., a summer period where outdoor water usage riseswith irrigation demand), such that a peaking factor may refer to therelative amount of fluctuation in comparing the additional water usageon the water infrastructure as compared to that peaking period. Forexample, in the month of August where water usage may already beexperience overall monthly peak demand, additional water usage duringthe hours of 6 .am-9 .a.m above that monthly peak demand may refer to apeaking factor for that hourly peak demand. In the example, additionalwater usage during the hours of 6 a.m.-9 a.m. may be indoor water usagesuch as people getting ready for work (e.g., showering) and/or lawnsbeing watering during non-peak sunlight intensity hours (e.g., non-peakmay refer to certain times outside of a range of hours defined by solarnoon). By using the methods 400, 450 the outdoor and indoor water usagecan be more evenly spaced across time to reduce the demand peaks,reducing the peak load on the main supply 122 and other components ofthe water infrastructure. In other words, the peak demand may besmoothed or compensated with this process. Because water infrastructuremay be designed to accommodate peak demand, by smoothing the peaks andevenly distributing the demands across multiple time-periods (e.g.,smoothing), older infrastructures can be configured to handle increasesin demand, without structural changes to the system.

To determine a peaking factor, the server 106 may utilize the receivedwater usage data to determine various types of peaking factors. Suchpeaking factors may include, but are not limited to: peaking factorsthat compare outdoor to indoor water usage, monthly overall water usageto an indoor water usage baseline, daily outdoor water usage to dailyoverall water usage, daily overall water usage to baseline annual waterusage. As can be seen from this description, various types of peakingfactors may be determine with respect to a ratio including various typesof water (e.g., indoor vs. outdoor), various time periods, and/orvarious combinations of types of water and time periods. The server 106may utilize the water usage data to perform various computations and/orcalculations to determine the peaking factor (e.g., calculating aratio). In some examples, the peaking factor may be computed based onvarious vectors that represent water usage over certain time-periods.Each vector may represent water usage according to a watering schedulethat includes a watering time length and/or a start time or according toa zone characteristic. The zone characteristic may be a native plantszone characteristic, a grass zone characteristic, or a potable waterzone characteristic. Other zone characteristics may include flow rate,stress threshold (e.g., user selection on plant stress or health), rootzone depth information, water capacity or soil type, crop coefficient,nozzle type, or the like. A peaking factor may be expressed as arelative measure of million gallons per day (“MGD) of water or directlyas an MGD numerical quantity.

After the operation 408, the server 106 determines whether the peakingfactor passes a threshold water usage at operation 412. A thresholdwater usage may refer to a water usage at which additional water usageleads to peak load or peak demand of water. For example, a thresholdwater usage at the flow controller 102 a-102 n may be 1 MGD. If waterusage passes above the threshold water usage, then the system 100experiences peak demand or peak load. From the perspective of the peakload or peak demand being represented as a peaking factor over a periodof time, the method 400 may adjust the water usage such that the peakingfactor is compensated to provide water to an infrastructure at abaseline water usage rate. Accordingly, the threshold water usage may beviewed as a cap on the water usage over time, with the peaking factor(s)being smoothed to compensate for fluctuations in load or demand of thewater infrastructure. To determine whether the peaking factor passes athreshold water usage at operation 412, the server 106 may compensate apeaking factor for adjustment of the watering schedules. If the peakingfactor is compensated to bring water usage below the threshold waterusage, the flow of method 400 process to operation 416 where the server106 adjusts the plurality of watering schedules of the flow controllers102 a-102 n. If the peaking factor is not compensated below a thresholdwater usage, the method 400 may continue computing or calculatingadjustments to the watering schedules to compensate the peaking factor.

In some examples, the server 106 may compensate the peaking factoraccording to various characteristics of the watering schedule orproperty type being watering. For example, to compensate the peaking,the server 106 may optimize and/or adjust characteristics of at leastone watering schedule of the flow controller 102 a-102 n. Suchcharacteristics of the watering schedule may include, but are notlimited to: a start time of the watering schedule, a stop time of thewatering schedule, an offset (e.g., a delay) of the watering schedules,a watering time length, a watering water pressure, a frequency of thewatering schedule, or an aspect of the outdoor or indoor water usage(e.g., stopping outdoor water usage but allowing indoor water usage tobe provided as scheduled).

Additionally or alternatively, the server 106 may optimize and/or adjustaspects of at least one watering schedule of the flow controller 102a-102 n based on a zone characteristic. A zone characteristic may be anycharacteristic in which a property with a connected flow controller 102a-102 n is classified. For example, zones may be classified accordingto: types of vegetation (e.g., native plants zone characteristic or agrass zone characteristic), types of water (e.g., potable vs.non-potable), weather zones, or zones classified according to aconnected valve controlled by a particular controller.

Additionally or alternatively, zones may also classify certainproperties (e.g., a selection of properties) associated with aparticular user characteristic of the respective property. For example,certain properties connected to the flow controller 102 a-102 n may beassociated with users (e.g., owners) of the properties that haveopted-in to receiving adjustments to their respective wateringschedules. In some examples, certain properties may be selected asproperties in particular zone by the server 106 based on theirassociation with a certain aspects of a water infrastructure, such as aparticular valve or flow controller. In another example, certainproperties may be selected as properties in particular zone according totheir association with a peaking factor (e.g., a local peaking factorparticular to the geographic region). For example, a system-wide waterevent could be associated with a peaking factor. The server 106 mayreceive an indication from the computation of the peaking factor or thewater usage data that an event has occurred. In such a case, due to theevent, the server 106 may select, as a zone, particular properties thatcould be affected by the event and/or compensate the peaking factor.Events may include a water shortage, water contamination (e.g., in areservoir), increased water demand from certain geographic regionsand/or localities, or any security-related event (e.g., possiblesecurity breach at water reservoir). Accordingly, the server 106 maycompensate the peaking factor according to various characteristics ofthe watering schedule and/or zone of a property. The server 106 mayoptimize and/or adjust the watering schedules in accordance with variouspossible methods. An example method 450 for compensating a peakingfactor is shown in FIG. 9.

Referring now to FIG. 8, the method 450 illustrates an example flow ofthe server 106 determining to compensate a peaking factor at operation412. Method 450 illustrates an iterative method beginning at operation454 and ending at the end operation 488, once the peak factor has beencompensated by at least optimizing and adjusting at least one aspect ofthe watering schedules. The watering schedules optimized and adjusted bythe server 106 may include schedules for irrigation and other outdoorusage, as well optionally indoor water use schedules, such as run timesfor washing machines, dishwashers, and other elements. In embodimentswhere the watering schedule corresponds to an irrigation schedule, theschedule includes times, dates, and run-times for various sprinklervalves, which may be determined by sprinkler zones having multiplevalves, or on a valve-by-valve basis. The method 400 begins at operation454. At operation 454, the server 106 optimizes watering schedulesaccording to a start time. The server 106 may compute or calculateindividual start times for various watering schedules to compensate anidentified peaking factor.

As an example of the operation 454, for an identified hourly peakingfactor in the afternoon hours, the server 106 may optimize the flowcontrollers 102 a-102 n for certain properties 130 a-130 n to activateat certain morning hours in the day, and other flow controllers forother properties may be set to activate on evening hours of that sameday. In this manner, each of the properties 130 a-130 n served by themain supply 122 may be alternatingly activated, such that the propertiesthat were to be activated in the afternoon hours are not activatedduring the identified hourly peaking factor. This spaces out the demandon the system, allowing for the system to compensate a peaking factor.In a specific example, the flow controller 102 a-102 n adjusts thewatering schedule for one or more properties 130 a-130 n to adjust forpeak demand on the main supply 122.

In optimizing the watering schedules at operation 454, the server 106may determine which options are available. Continuing in the sameexample, the server 106 may have utilized conditions differentconditions for the optimization: the properties that were to beactivated in the afternoon hours may be activated in solely the eveninghours; or, solely the morning hours. In the optimization process,however, the server 106 may determine that the split solution (e.g.,activating some in the morning hours and some in the evening hours)obtained a minimal flow in comparison to either of the sole solutions(e.g., solely evening hours or solely morning hours). In optimizing thisleast cost solution, the server 106 may utilize a least-squaresoptimization or other optimization techniques (e.g., a convexoptimization technique) to determine optimized watering schedulesaccording to a start time.

After operation 454, the flow of method 400 proceeds to operation 458.At operation 458, the server 106 adjusts the watering schedules based onthe optimized starting time. For example, the server 106 adjusts one ormore settings for each of the flow controllers 102 a-102 n. The settingsmay include watering amounts, watering schedules, notification types orfrequency, providing usage information to property owners, or the like.In such an example, the server 106 may specifically adjust a settingrelated to a start time, offset, delay, and/or stop time. The types ofsettings that may be adjusted may be varied based on the optimized starttime.

After operation 458, the server 106 determines whether a peaking factorhas been compensated at operation 462. The server 106 may computewhether the water usage included in the adjusted watering schedulesfalls below a threshold water usage. For example, a threshold waterusage at the flow controller 102 a-102 n may be 1 MGD. If water usagefalls below the threshold water usage, then the peaking factor has beencompensated. If the peaking factor has been compensated, the method 450may proceed along the “YES” flow to the end operation 488. At the endoperation 488, the method 450 ends; and the server 106 proceeds withmethod 400 after operation 412. However, if the peaking factor has notbeen compensated, the method 450 proceeds to operation 464 along the“NO” flow from operation 462.

At operation 464, the server 106 optimizes watering schedules based on azone characteristic. To optimize the watering schedules based on a zonecharacteristic, the server 106 may classify watering schedules fordifferent zones to compensate an identified peaking factor. Zonesinclude classifications of any characteristic in which a property with aconnected flow controller 102 a-102 n is classified. Some zones areclassified based on an association with a particular user characteristicof the respective property (e.g., a local peaking factor particular tothe geographic region). As an example of the operation 464, for aparticular zone with opted-in users of flow controllers 102 a-102 n, theserver 106 may optimize the flow controllers 102 a-102 n to activate theflow controllers of the connected properties of the flow controllers 102a-102 n, in coordination with activation of a zone classified as a grasszone at a non-peak time. This grass zone may be selected by the server106, as a zone with fewer properties than other zones. In some examples,a zone may be selected by the server 106 to optimize the wateringschedules with more properties, depending on the severity of the peakingfactor relative to other peaking factors. Accordingly, grass zone may bescheduled to be watered at a different time other than peak demand, asindicated by the peaking factor. This reduces the overall water usagefor the infrastructure, while ensuring that the grass zones are wateredat some scheduled time. As part of the example of method 450, the server106 may optimize this zone characteristic, in addition to the optimizedstart times in operation 454. For example, the grass zone may beselected to optimize the watering schedules, in addition to the adjustedstart times for some properties in the morning hours and others in theevening hours, described with respect to operation 454.

After operation 464, the flow of method 400 proceeds to operation 468.At operation 468, the server 106 adjusts the watering schedules based onthe zone characteristic. For example, the server 106 adjusts one or moresettings for each of the flow controllers 102 a-102 n. The settings mayinclude watering amounts, watering schedules, notification types orfrequency, providing usage information to property owners, or the like.In such an example, the server 106 may specifically adjust a settingrelated to a zone characteristic. For example, the server 106 mayactivate a flag of an individual flow controller 102 a-102 n having thezone characteristic. The types of settings that may be adjusted may bevaried based on the zone characteristic.

After operation 468, the server 106 determines whether a peaking factorhas been compensated at operation 472. The server 106 may computewhether the water usage included in the adjusted watering schedulesfalls below a threshold water usage. For example, a threshold waterusage at the flow controller 102 a-102 n may be 1 MGD. If water usagefalls below the threshold water usage, then the peaking factor has beencompensated. If the peaking factor has been compensated, the method 450may proceed along the “YES” flow to the end operation 488. At the endoperation 488, the method 450 ends; and the server 106 proceeds withmethod 400 after operation 412. However, if the peaking factor has notbeen compensated, the method 450 proceeds to operation 476 along the“NO” flow from operation 472.

At operation 476, the server 106 optimizes watering schedules accordingto a watering time length. The server 106 may compute or calculateindividual watering time lengths for various watering schedules tocompensate an identified peaking factor. As an example of the operation476, for an identified hourly peaking factor in the afternoon hours, theserver 106 may optimize the flow controllers 102 a-102 n for certainproperties 130 a-130 n to reduce the watering time of the wateringschedules associated with the afternoon hours to a short time periodthan originally scheduled. Accordingly, if the watering schedulesassociated with the afternoon hours were to be watered for one hour, thewatering time lengths may be reduced to a half hour. In optimizing thisschedule, the server 106 may determine which options are available. Thisspaces out the demand on the system, allowing for the system tocompensate a peaking factor. As part of the example of method 450, theserver 106 may optimize this watering time length, in addition to theoptimized start times in operation 454 and zone characteristic inoperation 464. For example, the adjusted watering time length of a halfhour for the watering schedules associated with the afternoon hours maybe selected to optimized the watering schedules, in addition to thenative plants zone and adjusted start times for some properties in themorning hours and others in the evening hours, described with respect tooperations 454 and 468.

After operation 476, the flow of method 400 proceeds to operation 480.At operation 480, the server 106 adjusts the watering schedules based onthe optimized watering time lengths. For example, the server 106 adjustsone or more settings for each of the flow controllers 102 a-102 n. Thesettings may include watering amounts, watering schedules, notificationtypes or frequency, providing usage information to property owners, orthe like. In such an example, the server 106 may specifically adjust asetting related to a watering time lengths. The types of settings thatmay be adjusted may be varied based on the optimized watering timelength.

After operation 480, the server 106 determines whether a peaking factorhas been compensated at operation 484. The server 106 may computewhether the water usage included in the adjusted watering schedulesfalls below a threshold water usage. For example, a threshold waterusage at the flow controller 102 a-102 n may be 1 MGD. If water usagefalls below the threshold water usage, then the peaking factor has beencompensated. If the peaking factor has been compensated, the method 450may proceed along the “YES” flow to the end operation 488. At the endoperation 488, the method 450 ends; and the server 106 proceeds withmethod 400 after operation 412. However, if the peaking factor has notbeen compensated, the method 450 proceeds back to the start of method450 at operation 454 along the “NO” flow from operation 484.

As can be appreciated, the method 450 may continue iteratively until thewatering schedules fall below a threshold water usage or until a settime to optimize expires. For example, the server 106, executing themethod 450 as a set of instructions, may receive a time-out flag from aclock that track a set time for optimization of the watering schedules.At the end of method 450 at operation 488 or when the method 450 timesout, the flow of method 400 may continue at operation 416, proceedingfrom the operation 412 that initiated the method 450. In the method 450,the flow of determining whether a peaking factor has passed a thresholdwater usage may be viewed as preferential to various characteristics ofthe watering schedule, the property type being watering, or a zonecharacteristic. With respect to the example of method 450, the order inthat method was to optimize, first, watering start time; second, zonecharacteristic; and third, watering time length. It can be appreciatedthat various optimizations and orders may be selected forcharacteristics of the watering schedule, the property type beingwatering, or a zone characteristic. Accordingly, additional examplemethods may optimize for two, four, or ten characteristics; and suchcharacteristic may be ordered according to various permutations.

Referring again now to FIG. 9, the method 400 continues with operation416. At operation 416, the server 106 adjusts watering schedules of theflow controllers 102 a-102 n. At operation 468, the server 106 adjuststhe watering schedules, for example, according to a starting time orwatering time length or based on the zone characteristic. In adjustingthe watering schedules, the server 106 generates an update to thewatering schedules to provide to individual flow controllers. The server106 adjusts, in an update, one or more settings for each of the flowcontrollers 102 a-102 n. The settings may include watering amounts,watering schedules, notification types or frequency, providing usageinformation to property owners, or the like. The server 106 mayconfigure instructions that set a flag in a setting of an individualflow controller 102 a-102 n related to characteristics of the wateringschedule, the property type being watering, or a zone characteristic. Inthe example including the method 450, the server 106 may specificallyadjust some settings of flow controllers related to a start time,watering time length, or zone characteristic that has been optimized bythe server 106.

After operation 416, the method 400 may proceed to operation 420. Inoperation 420, the server 106 may transmit the updated schedule orsettings to the flow controller 102 a-102 n and/or user devices 108a-108 n. For example, if the server 106 communicates the updatedwatering schedules or settings to the flow controller 102 a-102 n, theflow controller 102 a-102 n may also transmit the schedule or settingseither directly to the user devices 108 a-108 n. The transmission to theflow controller 102 a-102 n may include the updated watering schedules.Aspects of the watering schedules transmitted to the flow controller 102a-102 n may be varied as desired. For example, the update to a wateringschedule may only include an update regarding a zone characteristic(e.g., water-related event in a geographic region). The sever 106 maypush the settings changes to multiple controllers 102 a-102 nsimultaneously, individually, or in select groupings (see FIGS. 4, 6,and 7). Notifications may also be sent to the user devices 108 a-108 nregarding any updated watering schedule.

With continued reference to FIG. 9, after operation 420, the method 400may proceed to operation 424. In operation 424, the server 106determines whether feedback has been received. For example, the server106 may check every day or other select time period for updated datathat varies the water usage data. The server 106 may receive additionalwater usage data from an infrastructure database regarding the update tothe watering schedules. If the feedback received indicates that apeaking factor has not been compensated, the flow of method 400 proceedsalong the “YES” branch back to operation 421 to determine a peakingfactor that passes below a threshold water usage. If, however, thefeedback received indicates that a peaking factor has been compensated,flow process along the “NO” branch and the method 400 ends at endoperation 428. If the flow controllers 102 a-102 n are to be updated,the method 250 returns to operation 254. However, if the flowcontrollers 102 a-102 n do not need to be updated, the method 250 mayreturn to operation 260 and continue to operate the flow controllers 102a-102 n.

Using the methods 400, 450 of FIGS. 8 and 9, the system 100 can optimizewatering schedules for various properties 130 a-130 n that can allowovertaxed infrastructure to be able to accommodate current demand, aswell as expanding demands. As shown in FIG. 5, outdoor water usage, suchas a due to irrigation, peak demand can be 2.5 to 3 times that of thebaseline usage (e.g., typical indoor usage 272). As shown in FIG. 5,outdoor watering can generate a large demand on the infrastructure andmain supply 122 for small periods of time. By using the methods 400, 450the outdoor demand can be more evenly spaced across time to reduce thedemand peaks, reducing the peak load on the main supply 122 and othercomponents of the water infrastructure.

The server 106 may utilize the methods 400 and 450 iteratively, atvarying frequencies, to adjust and transmit watering schedules to flowcontrollers. For example, the server 106, executing the method 400 as aset of instructions, may request (e.g., a software call) to be executedupon receiving additional usage data or upon receiving feedback frominfrastructure databases at operation 424. In receiving such additionaldata (e.g., usage data or feedback), the server 106 may update thepeaking factor, such that it determines an updated peaking factor. Insome examples, the peaking factor may be represented in a watering modelfor the water infrastructure. In such a case, the watering model may beupdated with the updated peaking factor.

A simplified block structure for a computing device that may be usedwith the system 100 or integrated into one or more of the system 100 isshown in FIG. 10. For example, the server 106, user devices 108 a-108 n,flow controllers 102 a-102 n, and/or infrastructure databases 112 mayinclude one or more of the components shown in FIG. 10 and be used toexecute one or more of the operations disclosed in methods 200, 250,300, 310, 400, 450. With reference to FIG. 10, the computing device 500may include one or more processing elements 502, an input/outputinterface 504, a display 506, one or more memory components 508, anetwork interface 510, and one or more external devices 512. Each of thevarious components may be in communication with one another through oneor more busses, wireless means, or the like.

The processing element 502 is any type of electronic device capable ofprocessing, receiving, and/or transmitting instructions. For example,the processing element 502 may be a central processing unit,microprocessor, processor, or microcontroller. Additionally, it shouldbe noted that select components of the computer 500 may be controlled bya first processor and other components may be controlled by a secondprocessor, where the first and second processors may or may not be incommunication with each other.

The memory components 508 are used by the computer 500 to storeinstructions for the processing element 502, as well as store data, suchas the fluid device data, historical data, and the like. The memorycomponents 508 may be, for example, magneto-optical storage, read-onlymemory, random access memory, erasable programmable memory, flashmemory, or a combination of one or more types of memory components.

The display 506 provides visual feedback to a user and, optionally, canact as an input element to enable a user to control, manipulate, andcalibrate various components of the computing device 500. The display506 may be a liquid crystal display, plasma display, organiclight-emitting diode display, and/or cathode ray tube display. Inembodiments where the display 406 is used as an input, the display mayinclude one or more touch or input sensors, such as capacitive touchsensors, resistive grid, or the like.

The I/O interface 504 allows a user to enter data into the computer 500,as well as provides an input/output for the computer 500 to communicatewith other devices (e.g., flow controller 104, flow detector 102, othercomputers, speakers, etc.). The I/O interface 504 can include one ormore input buttons, touch pads, and so on.

The network interface 510 provides communication to and from thecomputer 500 to other devices. For example, the network interface 510allows the server 110 to communicate with the flow controller 104 andthe flow detector 102 through the network 114. The network interface 510includes one or more communication protocols, such as, but not limitedto WiFi, Ethernet, Bluetooth, and so on. The network interface 510 mayalso include one or more hardwired components, such as a UniversalSerial Bus (USB) cable, or the like. The configuration of the networkinterface 510 depends on the types of communication desired and may bemodified to communicate via WiFi, Bluetooth, and so on.

The external devices 512 are one or more devices that can be used toprovide various inputs to the computing device 500, e.g., mouse,microphone, keyboard, trackpad, or the like. The external devices 512may be local or remote and may vary as desired.

CONCLUSION

The foregoing description has broad application. For example, whileexamples disclosed herein may focus on residential water systems, itshould be appreciated that the concepts disclosed herein may equallyapply to other water systems, such as commercial properties. Similarly,although the system is discussed with respect to water sources, thesystem and methods may be used with substantially any other type offluid systems. Accordingly, the discussion of any embodiment is meantonly to be exemplary and is not intended to suggest that the scope ofthe disclosure, including the claims, is limited to these examples.

All directional references (e.g., proximal, distal, upper, lower,upward, downward, left, right, lateral, longitudinal, front, back, top,bottom, above, below, vertical, horizontal, radial, axial, clockwise,and counterclockwise) are only used for identification purposes to aidthe reader's understanding of the present disclosure, and do not createlimitations, particularly as to the position, orientation, or use ofthis disclosure. Connection references (e.g., attached, coupled,connected, and joined) are to be construed broadly and may includeintermediate members between a collection of elements and relativemovement between elements unless otherwise indicated. As such,connection references do not necessarily infer that two elements aredirectly connected and in fixed relation to each other. The exemplarydrawings are for purposes of illustration only and the dimensions,positions, order and relative sizes reflected in the drawings attachedhereto may vary

What is claimed is:
 1. A method for optimizing water usage in a waterinfrastructure comprising: receiving by one or more flow controllersusage data corresponding to demand on the water infrastructure;adjusting by a processor a water usage schedule for one or moreproperties based on the usage data; activating by the one or more flowcontrollers one or more water outlets for the one or more propertiesbased on the adjusted water usage schedule.
 2. The method of claim 1,wherein the one or more water outlets comprise a plurality of sprinklervalves.
 3. The method of claim 1, wherein the usage data comprises peakoutdoor watering times for a geographic location.
 4. The method of claim3, wherein the usage data comprises water source levels fluidlyconnected to the water infrastructure, expected growth in populationserved by the water infrastructure, and historical usage data of thewater infrastructure.
 5. A method for adjusting water usage in a waterinfrastructure comprising: receiving water usage data; determining apeaking factor for water usage, the peaking factor associated with waterusage at one or more flow controllers; determining that the peakingfactor passes a threshold water usage for the one or more flowcontrollers; and adjusting a plurality of watering schedules basedpartly on the determination that the peaking factor passed the thresholdwater usage, each watering schedule associated with a corresponding flowcontroller of the one or more flow controllers.
 6. The method of claim5, wherein the water usage data comprises usage data from a plurality ofpressure sensors of the water infrastructure, the method furthercomprising: determining an updated peaking factor for water usageassociated with the one or more flow controllers based at least partlyon the usage data; and adjusting the plurality of watering schedulesbased partly on the updated peaking factor.
 7. The method of claim 5,wherein the usage data comprises water trend data from a water utility,the plurality of watering schedules, or forecasted weather data.
 8. Themethod of claim 5, wherein adjusting the plurality of watering schedulescomprises: optimizing the plurality of watering schedules based on azone characteristic associated with a selection of properties; andadjusting the plurality of watering schedules based on the zonecharacteristic.
 9. The method of claim 8, wherein the zonecharacteristic comprises at least one of a native plants zonecharacteristic, a grass zone characteristic, or a potable water zonecharacteristic.
 10. The method of claim 8, wherein the selection ofproperties comprises at least one of a selection of opt-in properties, aselection of properties including at least one of the one or more flowcontrollers, or a selection of properties associated with the peakingfactor.
 11. The method of claim 8, wherein determining the peakingfactor for water usage comprises calculating a ratio including a type ofwater usage over a time period and an overall water usage for adifferent time period.
 12. The method of claim 5, further comprising:optimizing the plurality of watering schedules according to a start timefor at least one of the plurality of watering schedules; and adjustingthe plurality of watering schedules based on a plurality of optimizedstart times.
 13. The method of claim 5, further comprising: optimizingthe plurality of watering schedules according to a watering time lengthfor at least one of the plurality of watering schedules; and adjustingthe plurality of watering schedules based on a plurality of optimizedwatering time lengths.
 14. The method of claim 5, wherein the peakingfactor includes an event indication based on a water-related event, themethod further comprising: receiving the event indication regarding thewater-related event from a water utility; adjusting a plurality ofwatering schedules based partly on the determination that the peakingfactor passed the threshold water usage and based partly on a selectionof properties associated with the event indication.
 15. The method ofclaim 14, wherein the event affecting water flow comprises a watershortage, water contamination, increased water demand from a geographicregion, or a security-related event.
 16. The method of claim 14, whereinthe selection of properties comprises at least one of a selection ofopt-in properties, a selection of properties including at least one ofthe one or more flow controllers, a selection of properties associatedwith the peaking factor, or all properties associated with the waterinfrastructure.
 17. The method of claim 5, further comprising:transmitting the plurality of watering schedules; and transmitting anotification to a user associated with each adjusted watering schedule.18. An apparatus, comprising: a server coupled to infrastructuredatabases and a plurality of flow controllers, each flow controller ofthe plurality of flow controllers connected to at least one water outletof a plurality of water outlets, the server including a non-transitorycomputer readable media and configured to execute instructions stored onthe non-transitory computer readable media, the instructions comprising:determining a peaking factor for water usage based partly on water usagedata received from at least one flow controller of the plurality of flowcontrollers, the peaking factor associated with water usage at theplurality of flow controllers; adjusting a plurality of wateringschedules based partly on the peaking factor, each watering scheduleassociated with a corresponding flow controller of plurality of flowcontrollers.
 19. The apparatus of claim 18, wherein adjusting theplurality of watering schedules based partly on the peaking factorcomprises: generating an update to a watering model including theplurality of watering schedules; transmitting the update to the wateringmodel to at least one flow controller of the plurality of flowcontrollers.
 20. The apparatus of claim 18, wherein the server isconnected to infrastructure databases storing additional water usagedata thereon, the additional water usage data comprising environmentalfactors, utility information, water reservoir information, or watersource information, wherein determining the peaking factor for waterusage comprises determining the peaking factor based partly on the waterusage data received from at least one flow controller and the additionalwater usage data.